Storyline 360 Accessibility Conformance Report

Web Content Accessibility Guidelines 2.0

Level A (Yes)
Level AA (Yes)
Level AAA (Yes)

Web Content Accessibility Guidelines 2.1

Level A (Yes)
Level AA (Yes)
Level AAA (Yes)

Web Content Accessibility Guidelines 2.2

Level A (Yes)
Level AA (Yes)
Level AAA (Yes)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

Yes

EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11)  AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)

Yes

1.1.1 Non-text Content (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.1.1 (Web)
• 10.1.1.1 (Non-web document)
• 11.1.1.1.1 (Open Functionality Software)
• 11.1.1.1.2 (Closed Functionality Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide text alternatives for images, shapes, and other non-text objects using alt text, slide notes, or on-screen text. Storyline offers an AI-assisted option to generate draft alternative text, which authors review and edit before publishing.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.2.1 (Web)
• 10.1.2.1 (Non-web document)
• 11.1.2.1.1 (Open Functionality Software)
• 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide text transcripts for audio-only content and for video content that does not include descriptive audio. Storyline supports displaying transcripts using on-screen text, slide notes, layers, or interactive markers.

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.2.2 (Web)
• 10.1.2.2 (Non-web document)
• 11.1.2.2 (Open Functionality Software)
• 11.1.2.2 (Closed Software) 
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) 
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can add captions to prerecorded audio and video by importing caption files or creating them with Storyline’s built-in caption editor. Storyline offers an AI-assisted option to generate draft captions when media is added, recorded, or imported, which authors review and edit before publishing.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.2.3 (Web)
• 10.1.2.3 (Non-web document)
• 11.1.2.3.1 (Open Functionality Software)
• 11.1.2.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) 
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide audio description or a text-based alternative for video content that is not conveyed through existing audio, such as on-screen text, actions, and scene changes. Storyline supports this through separate audio tracks, on-screen text, layers, or slide notes.

1.3.1 Info and Relationships (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.3.1 (Web)
• 10.1.3.1 (Non-web document)
• 11.1.3.1.1 (Open Functionality Software)
• 11.1.3.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Storyline publishes semantic markup for common elements such as paragraphs, links, and lists, which supports navigation with assistive technologies. Authors can use text styles to identify headings and block quotes. Storyline offers an AI-assisted option to draft slide content and headings, which authors review and adjust to ensure proper structure before publishing.

1.3.2 Meaningful Sequence (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.3.2 (Web)
• 10.1.3.2 (Non-web document)
• 11.1.3.2.1 (Open Functionality Software)
• 11.1.3.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can define the reading order of slide content so screen reader users can understand the intended sequence and relationships. Storyline provides the Focus Order window to set and review this order.

1.3.3 Sensory Characteristics (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.3.3 (Web)
• 10.1.3.3 (Non-web document)
• 11.1.3.3 (Open Functionality Software)
• 11.1.3.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide text-based instructions that don’t rely only on shape, size, visual location, orientation, or sound. Storyline supports presenting these instructions using on-screen text, slide notes, or layers.

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.4.1 (Web)
• 10.1.4.1 (Non-web document)
• 11.1.4.1 (Open Functionality Software)
• 11.1.4.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide alternatives when color is used to convey information or instructions, such as adding text labels, icons, patterns, or other visual cues. Storyline supports presenting this information through on-screen text, shapes, images, and other design elements.

1.4.2 Audio Control (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.4.2 (Web)
• 10.1.4.2 (Non-web document)
• 11.1.4.2 (Open Functionality Software)
• 11.1.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can use built-in media controls, such as play/pause and volume, or create custom controls using buttons, links, and triggers. These controls are operable with keyboards and supported by screen readers.

2.1.1 Keyboard (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.1.1 (Web)
• 10.2.1.1 (Non-web document)
• 11.2.1.1.1 (Open Functionality Software)
• 11.2.1.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Partially Supports

Most Storyline 360 features can be operated using a keyboard. Drag-and-drop interactions are not currently keyboard accessible. Authors can provide keyboard-accessible alternatives, such as sliders, dials, radio buttons, or button groups, to support keyboard operation.

2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.1.2 (Web)
• 10.2.1.2 (Non-web document)
• 11.2.1.2 (Open Functionality Software)
• 11.2.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Storyline courses support keyboard navigation without trapping focus within content sections, allowing learners to move through and exit interactive areas using the keyboard.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.1.4 (Web)
• 10.2.1.4 (Non-web document)
• 11.2.1.4.1 (Open Functionality Software)
• 11.2.1.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Storyline supports keyboard shortcuts that use modifier keys to help prevent accidental activation. Learners can disable built-in keyboard shortcuts if they prefer. Authors can also create custom keyboard shortcuts using key-press triggers, which activate only when specific components have focus.

2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.2.1 (Web)
• 10.2.2.1 (Non-web document)
• 11.2.2.1 (Open Functionality Software)
• 11.2.2.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can design content without time limits, allowing learners to control the pace of reading and interaction. Storyline supports learner-controlled navigation and does not require automatic slide advancement or time-based content changes.

2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.2.2 (Web)
• 10.2.2.2 (Non-web document)
• 11.2.2.2 (Open Functionality Software)
• 11.2.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide mechanisms to pause, stop, or control moving, blinking, or auto-updating content. Storyline supports built-in controls and custom controls that allow learners to manage pacing.

2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.3.1 (Web)
• 10.2.3.1 (Non-web document)
• 11.2.3.1 (Open Functionality Software)
• 11.2.3.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can avoid using videos or animations that flash or blink more than three times per second. Storyline supports including video and animation content without requiring flashing effects.

2.4.1 Bypass Blocks (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.4.1 (Web)
• 10.2.4.1 (Non-web document) – Does not apply
• 11.2.4.1 (Open Functionality Software) – Does not apply
• 11.2.4.1 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

Storyline provides a skip navigation shortcut that allows screen reader users to bypass repetitive navigation and move directly to slide content when using keyboard navigation. This behavior is enabled by default in published courses.

2.4.2 Page Titled (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.4.2 (Web)
• 10.2.4.2 (Non-web document)
• 11.2.4.2 (Open Functionality Software) - Does not apply
• 11.2.4.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Storyline uses the course title as the page title displayed in the browser tab. Screen readers announce the page title when the course first launches, helping identify the content.

2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.4.3 (Web)
• 10.2.4.3 (Non-web document)
• 11.2.4.3 (Open Functionality Software)
• 11.2.4.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can define a custom focus order for interactive objects so keyboard and screen reader users can follow the intended sequence of content. Storyline provides a Focus Order window to set and review this order. Website videos and web objects are placed at the end of the focus order due to cross-domain limitations.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.4.4 (Web)
• 10.2.4.4 (Non-web document)
• 11.2.4.4 (Open Functionality Software)
• 11.2.4.4 (Closed Software
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide descriptive text for buttons and hyperlinks so learners understand their purpose. Storyline supports accessible names for interactive elements, which are announced by screen readers. Author guidance is available for adding alternative text where needed.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.5.1 (Web)
• 10.2.5.1 (Non-web document)
• 11.2.5.1 (Open Functionality Software)
• 11.2.5.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Storyline courses support touch-based interactions without requiring complex pointer gestures. Learners can complete interactions using simple taps or alternative input methods.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.5.2 (Web)
• 10.2.5.2 (Non-web document)
• 11.2.5.2 (Open Functionality Software)
• 11.2.5.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Interactive objects activate on mouse release rather than mouse press, allowing learners to move the pointer away from a target before activation.

2.5.3 Label in Name (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.5.3 (Web)
• 10.2.5.3 (Non-web document)
• 11.2.5.3.1 (Open Functionality Software)
• 11.2.5.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Authors can align alternative text and accessible names with visible on-screen labels to support consistent identification of controls.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.5.4 (Web)
• 10.2.5.4 (Non-web document)
• 11.2.5.4 (Open Functionality Software)
• 11.2.5.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 does not support motion-based input. Course interactions are not controlled by device movement.

3.1.1 Language of Page (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.1.1 (Web)
• 10.3.1.1 (Non-web document)
• 11.3.1.1.1 (Open Functionality Software)
• 11.3.1.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Storyline 360 includes a language identifier in the published output. Course authors select the language in the player text labels.

3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.2.1 (Web)
• 10.3.2.1 (Non-web document)
• 11.3.2.1 (Open Functionality Software)
• 11.3.2.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Changing focus in Storyline 360 does not trigger a change of context.

3.2.2 On Input (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.2.2 (Web)
• 10.3.2.2 (Non-web document)
• 11.3.2.2 (Open Functionality Software)
• 11.3.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide clear information about actions that change context before learners activate them.

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 does not include built-in help mechanisms within course content.

3.3.1 Error Identification (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.3.1 (Web)
• 10.3.3.1 (Non-web document)
• 11.3.3.1.1 (Open Functionality Software)
• 11.3.3.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Storyline 360 provides built-in alerts for required responses when using built-in question types. Authors can also use triggers, states, and layers to create custom validation and error messages.

3.3.2 Labels or Instructions (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.3.2 (Web)
• 10.3.3.2 (Non-web document)
• 11.3.3.2 (Open Functionality Software)
• 11.3.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide on-screen instructions to describe how to interact with slide content, including what information is expected in data-entry fields.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 does not include built-in mechanisms that require learners to re-enter the same information within a course.

4.1.1 Parsing (Level A)

Applies to:

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

EN 301 549 Criteria

• 9.4.1.1 (Web)
• 10.4.1.1 (Non-web document)
• 11.4.1.1.1 (Open Functionality Software)
• 11.4.1.1.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.

4.1.2 Name, Role, Value (Level A)

Also applies to:

EN 301 549 Criteria

• 9.4.1.2 (Web)
• 10.4.1.2 (Non-web document)
• 11.4.1.2.1 (Open Functionality Software)
• 11.4.1.2.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

The Storyline 360 player uses semantic structure, ARIA landmarks, and structured controls with a consistent order and hierarchy. Authors can label slide objects using on-screen text or alternative text to support screen reader interaction.

1.2.4 Captions (Live) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.2.4 (Web)
• 10.1.2.4 (Non-web document)
• 11.1.2.4 (Open Functionality Software)
• 11.1.2.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Not Applicable

Storyline 360 does not include real-time audio or video broadcasts.

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.2.5 (Web)
• 10.1.2.5 (Non-web document)
• 11.1.2.5 (Open Functionality Software)
• 11.1.2.5 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide audio descriptions for video content by recording or importing audio and syncing it with the slide timeline. When creating original videos, authors can include important visual details in the narration. For third-party videos, authors can link the video to the slide timeline and use cue points and triggers to pause playback, play an audio description, and then resume the video.

1.3.4 Orientation (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.3.4 (Web)
• 10.1.3.4 (Non-web document)
• 11.1.3.4 (Open Functionality Software)
• 11.1.3.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Storyline 360 courses support both landscape and portrait orientations through the responsive player. Authors should avoid instructions or interactions that rely on a specific device orientation so content remains usable if the orientation changes.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.3.5 (Web)
• 10.1.3.5 (Non-web document)
• 11.1.3.5.1 (Open Functionality Software)
• 11.1.3.5.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Does Not Support

Storyline 360 does not support programmatic identification of personal information input purposes or browser-based autofill. Course interactions typically collect learner responses rather than personal data. Authors can provide clear, visible labels and instructions so learners understand what information is expected.

1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.4.3 (Web)
• 10.1.4.3 (Non-web document)
• 11.1.4.3 (Open Functionality Software)
• 11.1.4.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can choose text and background colors that provide sufficient contrast for readability. On-screen text should have a contrast ratio of at least 4.5:1.
The modern player style is designed to meet minimum contrast requirements by default. When authors apply custom colors, they review and adjust contrast as needed.

1.4.4 Resize text (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.4.4 (Web)
• 10.1.4.4 (Non-web document)
• 11.1.4.4.1 (Open Functionality Software)
• 11.1.4.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

When authors use the modern player style, learners can use the modern player zoom controls and browser zoom on desktop to enlarge slide content. On mobile devices, learners can use pinch-to-zoom gestures.

When authors use player styles with a fixed slide size, learners can use browser zoom on desktops and pinch-to-zoom on mobile devices to enlarge content.

1.4.5 Images of Text (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.4.5 (Web)
• 10.1.4.5 (Non-web document)
• 11.1.4.5.1 (Open Functionality Software)
• 11.1.4.5.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can use on-screen text to present important information so it can be read by assistive technologies and adapted to user settings. When images of text are used, authors can provide the same information in accessible text elsewhere on the slide, such as on-screen text or slide notes.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.10 (Web)
• 10.1.4.10 (Non-web document)
• 11.1.4.10 (Open Functionality Software)
• 11.1.4.10 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Storyline 360 courses use a two-dimensional, slide-based layout with a fixed aspect ratio. Content is designed to zoom within the browser, but it does not reflow without changing layout or context. At higher zoom levels, learners may need to scroll horizontally and vertically.

WCAG allows this behavior for two-dimensional content such as presentations. When authors use the modern player style, learners can also use the built-in zoom controls to adjust the view.

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.11 (Web)
• 10.1.4.11 (Non-web document)
• 11.1.4.11 (Open Functionality Software)
• 11.1.4.11 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Authors can choose colors for user interface components and graphical elements that provide sufficient contrast against their backgrounds. Non-text elements, such as buttons and icons, should have a contrast ratio of at least 3:1.

The modern player style is designed to meet minimum non-text contrast requirements by default. When authors apply custom colors, they review and adjust contrast as needed. Contrast can be checked using common contrast evaluation tools.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.12 (Web)
• 10.1.4.12 (Non-web document)
• 11.1.4.12 (Open Functionality Software)
• 11.1.4.12 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Learners can use browser features and assistive tools, such as extensions, to adjust text properties like line spacing, letter spacing, and word spacing. Storyline 360 accessible text supports these adjustments in typical use without loss of content or functionality.

Authors can help support text spacing by using built-in text fields and avoiding images of text for essential content.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.13 (Web)
• 10.1.4.13 (Non-web document)
• 11.1.4.13 (Open Functionality Software)
• 11.1.4.13 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

Most content in Storyline 360 can be accessed without relying on hover-only interactions.

Some behaviors don’t yet fully meet this criterion. For example, certain object hover states can’t be dismissed using a keyboard command, and tooltips in built-in Likert scale questions aren’t hoverable or dismissible.

We’re investigating improvements. Authors can reduce reliance on hover-only content by presenting important information using on-screen text.

2.4.5 Multiple Ways (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.2.4.5 (Web)
• 10.2.4.5 (Non-web document) – Does not apply
• 11.2.4.5 (Open Functionality Software) – Does not apply
• 11.2.4.5 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

Storyline 360 includes built-in navigation options, such as the course menu, search field, and previous and next buttons. Authors can add additional navigation using interactive objects, including buttons, hyperlinks, layers, lightboxes, and triggers.

2.4.6 Headings and Labels (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.2.4.6 (Web)
• 10.2.4.6 (Non-web document)
• 11.2.4.6 (Open Functionality Software)
• 11.2.4.6 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can use text boxes and built-in text styles to add descriptive headings and labels that clarify the structure and purpose of slide content.

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.2.4.7 (Web)
• 10.2.4.7 (Non-web document)
• 11.2.4.7 (Open Functionality Software)
• 11.2.4.7 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Storyline 360 displays a visible focus indicator around the object that currently has keyboard focus. The focus indicator defaults to a high-contrast color, and authors can customize its appearance to align with their course design.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

When keyboard focus moves to an interactive object, Storyline 360 displays a visible focus indicator, including when focus first appears on the slide.

2.5.7 Dragging Movements (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Does Not Support

The built-in drag-and-drop interaction types require dragging and don’t provide a single-pointer alternative.
Authors can support this criterion by using alternative interaction patterns, such as buttons, sliders, or other selectable controls, to achieve similar instructional outcomes.

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Storyline player controls are designed to meet the minimum target size requirement of 24 by 24 CSS pixels. For custom interactive objects, authors determine the size and spacing of clickable areas.

3.1.2 Language of Parts (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.1.2 (Web)
• 10.3.1.2 (Non-web document)
• 11.3.1.2 (Open Functionality Software) – Does not apply
• 11.3.1.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Does Not Support

Authors can set a single course language using player properties. Storyline 360 doesn’t currently support assigning different screen reader languages to individual objects within the same course.

3.2.3 Consistent Navigation (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.2.3 (Web)
• 10.3.2.3 (Non-web document) – Does not apply
• 11.3.2.3 (Open Functionality Software) – Does not apply
• 11.3.2.3 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

Built-in navigation elements appear in consistent locations throughout a course. When authors create custom navigation, they can place and order those elements consistently across slides to support predictable navigation.

3.2.4 Consistent Identification (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.2.4 (Web)
• 10.3.2.4 (Non-web document) – Does not apply
• 11.3.2.4 (Open Functionality Software) – Does not apply
• 11.3.2.4 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

When authors reuse objects or interactions, they can identify them consistently so learners recognize their purpose. Consistent visuals and labels, such as using the same icon and descriptive text for downloadable resources, support a predictable user experience.

3.3.3 Error Suggestion (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.3.3 (Web)
• 10.3.3.3 (Non-web document)
• 11.3.3.3 (Open Functionality Software)
• 11.3.3.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Authors can provide feedback or instructions when learners respond incorrectly, helping them understand what’s expected and how to proceed.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.3.4 (Web)
• 10.3.3.4 (Non-web document)
• 11.3.3.4 (Open Functionality Software)
• 11.3.3.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

When activities involve entering or submitting information, authors can provide a confirmation step that allows learners to review and change their responses before continuing. This can be done using accessible elements such as layers, buttons, or confirmation prompts.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 courses don’t require learners to authenticate to access course content.

Authentication, when required, is handled by the hosting environment rather than the course itself.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.4.1.3 (Web)
• 10.4.1.3 (Non-web document)
• 11.4.1.3 (Open Functionality Software)
• 11.4.1.3 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 doesn’t provide a separate status message mechanism. Learner feedback and updates are presented in the slide content or through author-defined interactions, so this criterion is not applicable.

1.2.6 Sign Language (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can include a synchronized video of a sign-language interpreter to provide a sign-language alternative for prerecorded audio content.

1.2.7 Extended Audio Description (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can provide extended audio descriptions for video content. This can be done by pausing the video at specific points and presenting additional audio and text descriptions before resuming playback.

1.2.8 Media Alternative (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can provide text-based alternatives for multimedia content, such as offering a button or link that reveals a layer with a text description of the media.

1.2.9 Audio-only (Live) (Level AAA)

EN 301 549 Criteria– Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 doesn’t support live audio streams, so this criterion isn’t applicable.

1.3.6 Identify Purpose (Level AAA 2.1 and 2.2)

EN 301 549 Criteria– Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 courses don’t include a mechanism to programmatically identify the purpose of form input fields that collect personal user information, as described in this criterion. Text-entry fields are typically used for instructional responses rather than for personal data, so this criterion is not applicable.

1.4.6 Contrast (Enhanced) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can choose text and background color combinations that provide higher contrast for improved readability. On-screen text can be designed to reach a contrast ratio of 7:1 or higher.

1.4.7 Low or No Background Audio (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

When narration is present, authors can either avoid background audio or provide a control that allows learners to mute it.

1.4.8 Visual Presentation (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Learners can adjust text size, font, spacing, and colors using browser features or user stylesheets. Authors can avoid locking text settings that prevent these adjustments. See Storyline 360 documentation on accessible text for guidance.

1.4.9 Images of Text (No Exception) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can use real text instead of images of text, so the content works better with resizing and assistive technologies. If an image of text is necessary, provide an equivalent text alternative.

2.1.3 Keyboard (No Exception) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Partially Supports

Most Storyline 360 features can be operated using a keyboard. Drag-and-drop interactions are not currently keyboard accessible.

2.2.3 No Timing (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can give learners control over timing by using play and pause controls and avoiding time limits. If assessments are included, authors can allow learners to take as much time as needed to complete them.

2.2.4 Interruptions (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 courses do not include auto-updating or interruptive content by default. Authors can avoid adding content that interrupts learners unexpectedly.

2.2.5 Re-authenticating (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Storyline 360 does not log learners out after a period of inactivity. If an LMS requires re-authentication, authors can enable the resume feature so learners can continue where they left off.

2.2.6 Timeouts (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Storyline 360 courses do not time out due to inactivity. If an LMS applies session time limits, authors can enable the resume feature so learners can continue where they left off.

2.3.2 Three Flashes (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can avoid using content that flashes more than three times per second. If video or animation is included, review it to help ensure it does not exceed flash thresholds.

2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can avoid motion triggered by user interaction unless it is essential. If motion is included, authors can provide a way to turn it off or offer a static alternative.

2.4.8 Location (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can provide information about a learner’s location within a course, such as using the built-in menu or other on-screen indicators.

2.4.9 Link Purpose (Link Only) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can use clear, descriptive text for buttons and hyperlinks so learners understand their purpose without relying on surrounding content.

2.4.10 Section Headings (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can organize content into sections using scenes, menus, and on-screen headings. Storyline 360 supports accessible heading levels (H1–H4) through text styles to help structure content.

2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The player keeps the focused element visible and not covered by other content during keyboard navigation, including at supported zoom levels. Authors are responsible for ensuring that custom layouts or overlapping objects do not obscure focused elements.

2.4.13 Focus Appearance (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The focus indicator in the player is at least 2 pixels thick. Authors control focus indicator color through design choices and are responsible for ensuring sufficient contrast between the focus indicator and adjacent colors.

2.5.5 Target Size (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can design interactive elements, such as buttons and hotspots, to be at least 44 by 44 CSS pixels whenever possible to support accurate selection. Storyline player controls have defined minimum target sizes that increase when learners use browser or device zoom.

2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Learners can navigate courses using a mouse, keyboard, or supported touchscreen gestures. These input methods can be used without requiring learners to switch to a specific mechanism.

3.1.3 Unusual Words (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can define or explain unusual words and phrases using the built-in glossary feature or a custom glossary interaction.

3.1.4 Abbreviations (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can spell out abbreviations and acronyms or provide explanations using the built-in glossary feature or a custom glossary interaction.

3.1.5 Reading Level (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can write content as clearly and simply as possible. When text requires a higher reading level, authors can provide summaries or supplemental content to support understanding.

3.1.6 Pronunciation (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can provide pronunciation support for words whose meaning may be unclear from context. This can be done using the built-in glossary feature, a custom glossary interaction, or audio files that demonstrate correct pronunciation.

3.2.5 Change on Request (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors control whether slides change, layers open, or new windows launch. By default, these events occur in response to learner interaction rather than automatically, allowing learners time to read content and complete activities.

3.3.5 Help (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can provide contextual help throughout a course using slide notes, layers, or interactive markers.

3.3.6 Error Prevention (All) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Authors can require learners to confirm responses before final submission and provide options to review or retry individual questions or an entire quiz. Review and retry features are built into Storyline 360 and can be enabled by authors.

3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

Storyline 360 does not require learners to authenticate in order to access published content. Any authentication requirements are determined by the hosting environment or learning management system.

302.1 Without Vision

Supports

Storyline 360 output supports use without vision through screen readers, keyboard access, and structured content. Support depends on authoring choices.

302.2 With Limited Vision

Supports

Storyline 360 output supports use with limited vision through screen readers, keyboard access, zoom and text resizing, and sufficient color contrast. Support depends on authoring choices.

302.3 Without Perception of Color

Supports

Storyline 360 output supports use without color perception by conveying information through text, labels, and other visual indicators in addition to color. Support depends on authoring choices.

302.4 Without Hearing

Supports

Storyline 360 output supports closed captions for video content. For audio-only content, authors can provide equivalent access through on-screen text, transcripts, or slide notes. AI Assistant can help draft captions or text alternatives, which authors review and edit before publishing.

302.5 With Limited Hearing

Supports

Storyline 360 output supports closed captions for video content. Authors can add captions to videos and provide equivalent access for audio-only content through on-screen text, transcripts, or slide notes. AI Assistant can help draft video captions, which authors review and edit before publishing. Authors are responsible for ensuring captions and text alternatives are accurate and complete.

302.6 Without Speech

Supports

Storyline 360 output does not require speech input to complete interactions. Learners can navigate and respond using keyboard, mouse, or other supported input methods.

302.7 With Limited Manipulation

Partially Supports

Most Storyline 360 features can be operated using a keyboard. Drag-and-drop interactions are not currently keyboard accessible. Authors can provide keyboard-accessible alternatives, such as sliders, dials, radio buttons, or button groups, to ensure learners can complete activities without requiring precise mouse movement.

302.8 With Limited Reach and Strength

Supports

Storyline 360 output supports navigation using a mouse, keyboard, or touchscreen gestures. Authors can design interactions that do not require sustained holding, precise movement, or complex gestures, and can use simple selection methods such as buttons or standard form controls to support learners with limited reach or strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Supports

Storyline 360 output supports clear structure, consistent navigation, and readable text. Authors can design training to support learners with limited language, cognitive, or learning abilities by using plain language, short sentences, meaningful headings, and clear instructions. Visuals can be used to reinforce key points when they support understanding. For complex topics, authors can provide summaries or simplified explanations alongside detailed content. Authors are responsible for reviewing content for clarity and readability before publishing.

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.2 section

Conformance is addressed in the WCAG 2.2 section of this report. The applicable Level A and AA success criteria are detailed there.

502.2.1 User Control of Accessibility Features

Not Applicable

This requirement applies to platform software that provides accessibility features. Storyline 360 publishes HTML content that runs within supported browsers and operating systems and does not control platform-level accessibility settings.

502.2.2 No Disruption of Accessibility Features

Supports

Storyline 360 published output runs within supported browsers and operating systems and is designed to work with platform accessibility features. It does not override or disable operating system or browser accessibility settings.

502.3 Accessibility Services

Not Applicable

Criteria 502.3.1 through 502.3.14 apply to platform software that provides accessibility services and APIs. Storyline 360 publishes HTML content that runs in supported browsers and operating systems and does not provide platform accessibility services itself.

502.4 Platform Accessibility Features

Not Applicable

This requirement applies to platform software that provides accessibility features. Storyline 360 publishes HTML content that runs in supported browsers and operating systems and does not provide platform accessibility features itself.

503.2 User Preferences

Supports

Storyline 360 published output runs within supported browsers and respects user preferences set at the browser or operating system level, such as text size and zoom. Learners can use browser features or extensions to adjust font size, spacing, and other display settings. Guidance on creating accessible text is available in Storyline 360 documentation.

503.3 Alternative User Interfaces

Supports

Storyline 360 published output is designed to work with platform accessibility services provided by supported browsers and operating systems, including screen readers and other assistive technologies.

503.4.1 Caption Controls

Supports

When captions are provided for video content, the course player displays a closed-caption control alongside other media controls, such as volume, at the same menu level.

503.4.2 Audio Description Controls

Supports

Storyline 360 does not include a dedicated audio description control in the course player. Authors can provide audio description by incorporating extended descriptions into the video timeline or by creating interactions that pause the video and present additional audio and text. When audio description is included in the media, it uses the standard media playback controls in the player.

504.2 Content Creation or Editing

Not Applicable

This report evaluates Storyline 360 published learner output. Content creation and editing features of the authoring application are outside the scope of this VPAT.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

This report evaluates Storyline 360 published learner output. Format conversion and content import features of the authoring application are outside the scope of this VPAT.

504.2.2 PDF Export

Not Applicable

This report evaluates Storyline 360 published learner output. PDF export functionality of the authoring application is outside the scope of this VPAT.

504.3 Prompts

Not Applicable

This report evaluates Storyline 360 published learner output. Authoring prompts and guidance features are outside the scope of this VPAT.

504.4 Templates

Not Applicable

This report evaluates Storyline 360 published learner output. Template and content library features of the authoring application are outside the scope of this VPAT.

602.2 Accessibility and Compatibility Features

Supports

Accessibility and compatibility features of Storyline 360 are described in the product documentation and user guides. Additional guidance is available in knowledge base articles on the support site.

602.3 Electronic Support Documentation

Supports

Support documentation for Storyline 360 is available electronically on the Articulate website. Documentation is provided in web-based formats. Accessibility information, including the company's accessibility policy, is available on the website.

602.4 Alternate Formats for Non-Electronic Support Documentation

Not Applicable

Support documentation for Storyline 360 is provided electronically. Non-electronic documentation is not offered.

603.2 Information on Accessibility and Compatibility Features

Supports

Information about accessibility and compatibility features is available through Storyline 360 support services, including Artie (chat support), email, live chat, community forums, webinars, user guides, and knowledge base articles.

603.3 Accommodation of Communication Needs

Supports

Storyline 360 support services are available through multiple communication channels, including email and chat. Customers can request accommodations to support specific communication needs when contacting support.

4.2.1 Usage without vision

Supports

Storyline 360 output supports use without vision through screen readers, keyboard access, and structured content. Support depends on authoring decisions.

4.2.2 Usage with limited vision

Supports

Storyline 360 output supports use with limited vision through screen reader compatibility, keyboard access, scalable text, and configurable visual presentation. Text contrast, color use, and readability depend on authoring decisions.

4.2.3 Usage without perception of colour

Supports

Storyline 360 output supports use without perception of colour when information is not conveyed by colour alone. Support depends on authoring decisions.

4.2.4 Usage without hearing

Supports

Storyline 360 output supports use without hearing through captions and visual alternatives for audio content. Authors can provide equivalent access using on-screen text, transcripts, or slide notes. AI-assisted features can help draft captions or text alternatives, which authors review and edit before publishing. Support depends on authoring decisions.

4.2.5 Usage with limited hearing

Supports

Storyline 360 output supports limited hearing with captions and visual alternatives for audio content. Authors can also provide transcripts to support understanding. AI-assisted features can help draft captions or text alternatives, which authors review and edit before publishing. Support depends on authoring decisions.

4.2.6 Usage with no or limited vocal capability

Supports

Storyline 360 output does not require speech input to complete interactions. Learners can navigate and respond using keyboard, mouse, or other supported input methods.

4.2.7 Usage with limited manipulation or strength

Partially Supports

Storyline 360 output supports navigation using a mouse, keyboard, or touchscreen gestures. Authors can design interactions that do not require sustained holding, precise movement, or complex gestures, and can use simple selection methods such as buttons or standard form controls to support learners with limited reach or strength. Support depends on authoring decisions.

4.2.8 Usage with limited reach

Supports

Storyline 360 output supports navigation using a mouse, keyboard, or touchscreen gestures. Authors can design interactions that do not require extended reach or complex gestures. Support depends on authoring decisions.

4.2.9 Minimize photosensitive seizure triggers

Supports

Storyline 360 output supports minimizing photosensitive seizure triggers when authors avoid content that flashes or blinks more than three times per second. Support depends on authoring decisions.

4.2.10 Usage with limited cognition, language or learning

Supports

Storyline 360 output can be used by learners with limited cognitive, language, or learning abilities when authors create clear, well-structured content and provide appropriate guidance and feedback. Support depends on authoring decisions.

4.2.11 Privacy

Supports

Storyline 360 output supports accessible use without requiring learners to disclose a disability or personal information. Accessibility features are available without additional identification. Support depends on authoring decisions that include user input or data collection.

7.1 Caption processing technology

7.1.1 Captioning playback

Supports

Storyline 360 output supports caption playback for video content. Authors can add captions to videos, and learners can enable captions using the built-in player controls. Support depends on authoring decisions.

7.1.2 Captioning synchronization

Supports

Storyline 360 output supports synchronized captions for video content. Authors can adjust caption timing to align with audio. Support depends on authoring decisions.

7.1.3 Preservation of captioning

Not Applicable

Storyline 360 does not transmit or transform video content in a way that would remove or alter embedded caption data.

7.1.4 Captions characteristics

Partially Supports

Storyline 360 output provides captions that authors configure during development. Learners can enable or disable captions during playback. Caption appearance settings are not user-adjustable in the published player.

7.1.5 Spoken subtitles

Not Applicable

Storyline 360 does not provide functionality to convert captions to synthesized speech during video playback.

7.2.1 Audio description playback

Supports

Storyline 360 output supports playback of video content with audio description. Authors can include audio description tracks or provide equivalent media alternatives. Support depends on authoring decisions.

7.2.2 Audio description synchronization

Supports

Storyline 360 output supports synchronized audio descriptions for video content. Authors can align audio description with video timing or configure playback to pause and resume as needed. Support depends on authoring decisions.

7.2.3 Preservation of audio description

Not Applicable

Storyline 360 does not transmit or transform video content in a way that would remove or alter included audio description.

7.3 User controls for captions and audio description

Partially Supports

Storyline 360 output allows learners to enable or disable closed captions during playback. Separate user controls for audio description are not provided in the built-in player. Support depends on how authors design and present audio description.

12.1.1 Accessibility and compatibility features

Supports

Accessibility features and information about compatibility with assistive technologies are documented in the Storyline 360 user guide and related knowledge base articles on our support site.

12.1.2 Accessible documentation

Supports

Storyline 360 documentation is provided as web content and is designed to align with applicable WCAG requirements.

12.2.2 Information on accessibility and compatibility features

Supports

Information about accessibility and compatibility features is available through Storyline 360 support services, including Artie (chat support), email, live chat, community forums, webinars, user guides, and knowledge base articles.

12.2.3 Effective communication

Supports

Support services are available through multiple communication channels, including email and text-based chat. We can accommodate specific communication needs upon request.

12.2.4 Accessible documentation

Supports

Documentation provided through Storyline 360 support services is available in accessible electronic formats and published as web content aligned with applicable WCAG requirements.